Repository navigation
issue-tracker 0.3.0: Sync this table to GitHub (#177 item 14) - #276
Merged
Merged
Conversation
On an issue-v1 table the app didn't make, the app offers "Sync this table to GitHub": it asks for the host's "Allow editing" when the row grant doesn't cover its row-extras, keeps a binding under the App (synced-table, repository, sync state, comments folder), and then syncs that table as its own: compare on open, review before send, the same conflict rules, bookkeeping on the rows. Existing rows stay local until Publish to GitHub, rows are never deleted, the table is never written, and a lapsed grant pauses the sync. The App now renders issue-v1 and declares its row extras from the first open, and Atomic's localId joins the row extras (the Bridge sets it on imported rows). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts: # integrations/README.md
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 37816143 | Triggered | Generic High Entropy Secret | 543db78 | integrations/timesheets/live/fakeClockify.ts | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On an
issue-v1table the GitHub issues app didn't make, it now offers Sync this table to GitHub (#177 §6.2 item 14), following calendar 0.3.0 (#272). It:requestRowAccess) when the row grant doesn't cover the App'srow-extras;synced-table, the repository, sync state and a comments folder) and never writes the table itself;Two related changes:
issue-v1and declares its row extras from the first open, so "+ Add view" offers it before a repository is bound.localIdjoins the row extras, because the Bridge sets it on imported rows.Release: bundle 160,628 bytes, limit 173 KiB. Catalog entry 0.3.0, still
enabled: false. Usertest isusertest-7.Tests:
app/syncTable.test.ts(12 tests, against a fake host that enforces the pinned grant scope), plus view tests.Checks: issue-tracker unit (236) and e2e (2/2, run twice). Also: tooling tests 251/251, apps and ontology checks, certify, e2e tsc, oxlint (0 errors) and oxfmt.
Part of #177 (item 14 for issue-tracker).
🤖 Generated with Claude Code